date:
attendees:
tags:
- Rounding
At the beginning of the session, please consent if it is ok for the session to be recorded, solely for the ability for AI to summarize for our mutual benefit and recall next quarter. You can decline if you wish.
Please populate the table below (the reflective columns) ahead of our rounding meeting. We will use this document to co-assess technical leadership maturity and systems design thinking, not to run status updates.

I. The Leadership Competency Matrix (The 6 Pillars)
Instructions: Assess your current performance level for each pillar using the calibration scale below. Prioritize High-Fidelity Examples (artifacts like a documented process, package updates setup, telemetry configuration, or communication logs) over verbal anecdotes.
Calibration Scale:
- Emerging: Aware of expectations; applies them inconsistently or with significant support.
- Practicing: Meets expectations reliably and independently.
- Leading: Exceeds expectations; raises the bar for peers and actively coaches others.
- Shaping: Operates at the next level's expectations; changing how the broader organization works.
| Category | Self-Assessment <br>(Emerging/Practicing/Leading/Shaping) | Reflection of High-Fidelity Examples | Next: Strategic Focus | Next: 30-Day Focus |
|---|---|---|---|---|
| :--- | :--- | :--- | :--- | :--- |
| 1. Get Stuff Done <br>(Optimizing velocity, quality, flow, and DORA metrics) | [Links to PRs, DORA dashboards, backlog items] | (Focus / Maintain / Park) | (To be completed together) | |
| 2. Technical Skills <br>(Lean architecture, KISS/YAGNI, site reliability, backups) | [Links to architecture diagrams, post-mortems] | (Focus / Maintain / Park) | (To be completed together) | |
| 3. Security & SDLC <br>(Embedding security practices, vulnerability triage) | [Threat models, dependency audits, compliance logs] | (Focus / Maintain / Park) | (To be completed together) | |
| 4. Developer Culture <br>(Autonomy, psychological safety, egoless programming) | [Coaching frameworks, 1:1 templates, promo paths] | (Focus / Maintain / Park) | (To be completed together) | |
| 5. Communications <br>(Loops upward, laterally with product, and downward) | [Status reports, lateral alignment logs, RFC drafts] | (Focus / Maintain / Park) | (To be completed together) | |
| 6. Outcomes & Value <br>(Measurable business value, de-risking initiatives) | [Product opportunity assessments, pilot metrics] | (Focus / Maintain / Park) | (To be completed together) |
II. Systems Design & Architectural Judgment
To be completed prior to the session. Walk through one recent technical decision, architectural tradeoff, or dependency choice you or your team made. Explain the reasoning behind it, the alternatives considered, and what you learned from the outcome.
[Discuss architectural decision and tradeoffs here]
III. Strategic Alignment & Discussion Topics
To be completed by the Leader prior to the meeting. What are the systemic or structural blockers you are facing? What frustrates you and you wish were different? Where do you feel you need more support?
[Answer here, optional]
IV. Feedback for your Supervisor
How can I support you better, or be a better leader for you or your team? Constructive critical feedback is highly welcomed.
[Answer here, optional]
V. Pasted Meeting Transcript
[Paste transcript here]
Generated for the Technology Growth Program.